chore(release): 3.1.1 - #243
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts 3.1.1 for #242, the
--strictflag.PATCH is right here:
--strictis a new opt-in flag whose default leaves every existing behaviour byte-identical. No schema surface moves, no existing exit code changes, and all nine--no-buildcall sites keep their current results. Nothing a consumer relies on shifts unless they ask for it.Why this needs to ship rather than wait
python-sdk
release/2.0(v2.0.0-rc.3) runs the analyzer through the wheel's bundledjdk4pyJVM, which has nojavac. So every SDK Java user at-a 2or above silently loses the RTA overlay and the L4 semantic ddg — exit 0, aWARNon stderr nobody reads, and a thinner graph indistinguishable from a complete one.--strictis the only way for that caller to detect it.The SDK pin is exact (
codeanalyzer-java==3.1.0), so a lockstep bump to 3.1.1 onrelease/2.0follows this release. That is tracked as the propagation item on #242.Gates
Re-run on this commit before tagging; results recorded on the tag.